-
Notifications
You must be signed in to change notification settings - Fork 2.3k
fix issue 18446 NPE by making sure scoreSupplier.get() returns non-null scorer #19650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix issue 18446 NPE by making sure scoreSupplier.get() returns non-null scorer #19650
Conversation
…ll scorer Signed-off-by: Yao Zou <[email protected]>
e325aab
to
19d098a
Compare
❌ Gradle check result for 19d098a: FAILURE Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Thanks @haruki1243, the spotlessJavaCheck gradle task failed, please run |
Weight subQueryWeight = subQuery.createWeight(searcher, subQueryScoreMode, 1.0f); | ||
|
||
return new Weight(this) { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would need a test for this change as well
Signed-off-by: Yao Zou <[email protected]>
4e4d047
to
29f7ccd
Compare
Thank you so much for your reply. I have made the requested changes, including apotless formatting, tests and changelog I added test cases to ScriptScoreQueryTests and ScriptScoreQueryIT. both pass. You can try to replace the implementation of ScriptScoreQuery with the old one, and you will see both of them fail. Regarding yaml rest tests, sorry I didn't find tests that uses script score in those yaml tests, and ScriptScoreQueryIT seems to be the right place for its integration test instead. |
❌ Gradle check result for 29f7ccd: null Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change? |
Looks like Jenkins is down <title>403 Forbidden</title> 403 Forbiddenjq: parse error: Invalid numeric literal at line 1, column 7 QUEUE_URL wait for jenkins to start workflow Check if queue exist in Jenkins after triggering Use queue information to find build number in Jenkins if available |
Description
fix issue 18446 NPE by making sure scoreSupplier.get() returns non-null scorer
Related Issues
Resolves #[18446]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.